Skip to content

Revert "fix(gix-index): handle loongarch64-musl stat struct field names"#2455

Merged
Byron merged 1 commit intoGitoxideLabs:mainfrom
huajingyun01:main
Mar 12, 2026
Merged

Revert "fix(gix-index): handle loongarch64-musl stat struct field names"#2455
Byron merged 1 commit intoGitoxideLabs:mainfrom
huajingyun01:main

Conversation

@huajingyun01
Copy link
Contributor

This reverts commit 7e25c34.

The issue was fixed in libc: rust-lang/libc#4958

Copy link
Contributor

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: afe154c375

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

target_os = "hurd",
all(target_arch = "loongarch64", target_env = "musl")
)))]
#[cfg(not(any(target_os = "aix", target_os = "hurd")))]
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Restore loongarch-musl timespec field handling

This revert drops the loongarch64-musl branch from the cfg guard, so that target now compiles against self.0.st_mtime/st_mtime_nsec again; with libc = "0.2.180" still allowed in gix-index/Cargo.toml (line 60), that reintroduces the same build failure fixed in 7e25c34 because stat exposes st_mtim/st_ctim fields there. In practice, any consumer or lockfile still on libc 0.2.180 and building loongarch64-unknown-linux-musl will fail to compile this crate unless they manually bump libc.

Useful? React with 👍 / 👎.

@Byron
Copy link
Member

Byron commented Mar 12, 2026

Sorry for the long wait, and thanks @weihanglo for your appearance. That helped me to prioritise.

@Byron Byron merged commit ab36136 into GitoxideLabs:main Mar 12, 2026
30 checks passed
@EliahKagan
Copy link
Member

Will this change appear as intended in the changelog, or should something else be done to achieve that? I don't think cargo-smart-release recognizes commit messages of the form Revert "..." where ... is conventional.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants